ci: serialise gh-pages Allure pushes across CI + E2e - #119
Merged
Conversation
CI's Allure Report job and E2e's job both push to gh-pages on every push to main (4 writers, no coordination) — concurrent pushes race and the loser fails with non-fast-forward. Share one job-level concurrency group so they queue instead. Closes 118 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Every push to
mainfiresci.yml(Allure Report job → 1 gh-pages push) ande2e.yml(API + E2e job → 3 gh-pages pushes) with noconcurrencycoordination. The 4 writers race on thegh-pagesbranch; the loser fails with non-fast-forward.Hit on #117's merge (
490df1801) — CI failed in 13s at "Push raw unit+integration results to gh-pages cache", re-run passed. Flaky, not deterministic. Pre-existing; unrelated to that PR's contents.Fix
Shared job-level
concurrency: { group: gh-pages-allure, cancel-in-progress: false }on both jobs → they queue instead of colliding. Unit-test jobs still run in parallel with E2e; only the gh-pages writers serialise.Closes #118
🤖 Generated with Claude Code